Description of your changes

This PR makes slight changes to the integration test cases that assert the behavior of the Idempotency utility in the event of Lambda timeouts.

The implementation of the utility hasn't changed, but in the tests we are now expecting a different number of logs as well as a different message for functions that timeout.

I am not 100% sure about why, also because I can't test the old behavior, but it seems that Lambda functions timing out now return a different number of logs when invoked API. This resembles changes that were made by the new-ish Advanced Logging Configuration feature by Lambda, but as I said I'm not entirely sure.

Given that the implementation is the same and the changes are not on our side nor in our tests but rather in the way Lambda logs a timeout event, I decided to not investigate further and use the time elsewhere.

Related issues, RFCs

Issue number: #2076

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.